This program is SHAREWARE. I don't care if you just have it hanging around, but if you find it useful, be considerate and send $35.00 to make me feel good. You will note that I have not disabled any features or added an expiration date.
I can be contacted at:
Stephen Knight
c/o JSR Synergetics
1115 East Main St.
Rochester, NY 14609
or CompuServe: 76377, 52
----------
Version 1.21 Info, January 16, 1990:
Previously released version: 1.2
----- Differences between the previously released version and this one: -----
Shift left/right:
- Now deals with selected portions in a more civilized manner (ie: correctly).
- The problem with shifting when sample #0 has been displayed has been fixed.
Zoom in/out:
- Selected areas remain selected when zooming in and out.
Waveform selection:
- The time indicators now follow the mouse as portion of the signal is selected.
- It is no longer possible to select a nonexistant portion of the signal. This problem occurred when the signal had been shifted to the left and the end of the signal was visible.
Waterfall display:
- The new scale factor is 0.10, instead of 1.0. This will not effect a user much since this is a response to other changes in FFT computations.
----------
Version 1.2 Info, January 11, 1990:
Previously released version: 1.0
----- Differences between the previously released version and this one: -----
Waterfall display:
- The waterfall spectal display now deals with hidden lines in a more acceptable fashion (ie: they are now produced in "publishable" form).
- The waterfall spectral function can be canceled with Command-period.
New functions:
- The new function 'Extract' exists under the 'Edit' menu. When selected, 'Extract' will copy the selected portion of the current signal area into a new file. This allows the user to create new files with only a portion of the original, yet not have to go thru the hassle of cutting the preceding or subsequent portions of the file to get the desired section
Other modifications:
- The left and right arrow keys will scroll you thru the signal faster than before. Previously, the arrow keys scrolled at 1/10th the displayed signal per keystroke. Now it will scroll at 1/4th (which seems far more acceptable).
- File i/o efficiency has been improved allowing for less time occupied with opening and closing (the bad news is: floppy i/o is still slow).
- "Zoom" (in and out) and "Magnification" no longer needs a wave area to be selected. It immediately operates on the most recently selected wave area (like cut/copy/paste etc.).
- Command-keys have been added to most of the pulldown-menus. To provide for a bit more mnemonic styling, this entailed shifting some of the command keys to new positions/meanings (Sorry).
***** NOTE ***** While not all menu items have command-keys associated with them, they will function if you give them one. Please, if you do decide to change the command keys around, be careful and be aware of command-key limitations (if you don't know what I'm referring to...don't try it).
Dead bugs:
- When dealing with a MacRecorder file digitized at 7500Hz, SignalEditor v1.0 would set the sampling rate at 7333Hz. This problem has been corrected.
- A window update problem occurring after a file has been closed has been fixed. This bug appeared when a spectral window was first opened.
----- End of changes -----
Online HELP: Look under the 'About SignalEditor' for more of an explanation as to what the program is capable of doing. Also, the 'Settings' item under the 'Spectrum' menu has a help function that can give specific information as to what you would be setting.
----------
Some answers to the inevitable questions:
"The version I have complained about being a Mac II or later version"
Ñ I have two versions (SignalEditor and SignalEditor II) that should be traveling together. One is for the Mac II series or later, and uses code for the 68020/68881 (or later) processors. If you have the wrong one, check with your source. If you don't have any luck, check macserve@pucc or CompuServe (the better bet).
----------
"It seems to spend a lot of time accessing the disk when opening and closing the file and cut/paste/copy seems to do alot too."
The problem with editing signals comes from a choice between speed and the number of samples that fit into memory. I could have made the program try to load in ALL the samples when editing a signal, this would have made the program extremely fast. Unfortunately, there is always going to be the case of too many samples, so you would only be able to work with files that had fewer samples than you had memory.
I decided to compromise. The program only keeps the samples in memory that it needs at one time (currently 50K samples). The rest are kept in a temporary file until needed. When asked to display more samples (like a signal 60K samples long), it cheats and only shows the first 50K samples of the area selected. Since the samples are primarily on disk, cut/paste/copy do a very brute force shifting of the necessary samples to/from their appropriate spot. It may be crude, but it seems to work. When I figure out a better way, I'll be sure to put it in, but so far everything I've thought of has had some nasty drawbacks.
----------
"Ok, so it only displays a certain amount. How do I get at the rest of it?"
To get around the problem, I implemented two keystrokes that let you scroll through the signal (albeit slowly). They are, the LEFT ARROW and RIGHT ARROW keys. Each time you hit one, the current signal area in use will scroll the signal, either left or right, by approximately 25%. The larger the amount of time displayed, the greater the scrolling effect.
----------
"When I do the waterfall spectrogram or spectral slices on my SE/Mac+, it goes very slowly."
While my FFT routine is not the fastest, none are very quick. When it comes to signal processing, horsepower is a vital neccessity.
----------
"There's a bug here, now what?"
Although there are bound to be some 'features' that people don't like, I will try to compromise if enough registered users complain. If it is a bug, please send me a description, with as much technical detail as possible. I can be reached through the information on the 'About...' dialogs. If I can eliminate it, I promise to send you a new version, hopefully without the bug.
----------
"How about..."
If it doesn't look too bad to implement, sure. Warning: I might not have any idea how to implement it, so you might have to explain how (slowly). An ongoing dialog with registered users will insure improvement and expanded utility in future releases.